Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CROM-6916 Fix support for optional SFS runtime attributes #6755

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

kshakir
Copy link
Contributor

@kshakir kshakir commented May 7, 2022

No description provided.

Comment on lines 64 to 93
("present optional memory", "Float? memory_gb", Map("memory" -> WomString("3 GB")), Option(MemorySize(3, MemoryUnit.GB)).valid),
("missing optional memory", "Float? memory_gb", Map(), None.valid),
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the reviewers:

This Float? memory_gb declaration used to work but stopped at some point, along with a few other declarations listed in this test. The symptom is that on Cromwell 78 when defined as optional in the SFS backend the memory runtime attribute still needs to be defined for tasks or the workflow fails.

The Float? memory_gb declaration is both already:

@kshakir kshakir changed the title Fix support for optional SFS runtime attributes CROM-6916 Fix support for optional SFS runtime attributes May 10, 2024
@kshakir kshakir force-pushed the ks_sfs_opt_rt_attr branch from e9b3515 to 4d90157 Compare May 10, 2024 23:50
@kshakir kshakir requested a review from a team as a code owner May 10, 2024 23:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant